System and method of transmitting data by using widget window

ABSTRACT

A system and method of transmitting data by using a widget window are provided. A method of transmitting, by a first device, a file by using a widget window includes selecting a file stored in the first device, and moving the file to the widget window, when the file is moved to the widget window, displaying a device selection list, and, when at least one device is selected from the device selection list, providing the file to the selected device, wherein the file is provided to the selected device via a second device that is connected with the first device.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation application of prior application Ser.No. 13/768,676, filed on Feb. 15, 2013, which claimed priority under 35U.S.C § 119(a) of a Korean patent application number 10-2012-0015892,filed on Feb. 16, 2012, in the Korean Intellectual Property Office, thedisclosure of which is incorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a system and method of transmittingdata by using a widget window. More particularly, the present inventionrelates to a system and method of transmitting data to a device, whichis selected by using a widget window, via another device.

2. Description of the Related Art

Recently, contents such as pictures, moving pictures, and the like thatare generated by using smart phones have increased dramatically, and asthe smart phones have improved functions and office applications thatare widely used, there is an increasing need to share data of a PersonalComputer (PC) with mobile phones. Also, various services are provided toshare data between a PC and a mobile phone by using a PC client, a cloudservice, a window searcher, or the like. However, since it is requiredto use a Universal Serial Bus (USB) cable or to apply an account to amobile phone and then to configure complicated settings to connect a PCand the mobile phone, a troublesome procedure is required to beperformed to share data. Thus, there is a demand for a technology toeffectively detect a device by using an address book stored in a mobilephone and transmit data to the detected device via the mobile phone.

SUMMARY OF THE INVENTION

Aspects of present invention are to address at least the above-mentionedproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the present invention is toprovide a system and method of effectively selecting a transmissiontarget using a widget window and transmitting data to the selecteddevice.

Another aspect of the present invention is to provide a system andmethod of detecting a transmission target using a widget window from anaddress book stored in a source device and providing data to thetransmission target via the source device.

According to an aspect of the present invention, a method oftransmitting, by a first device, a file by using a widget window isprovided. The method includes selecting a file stored in the firstdevice and moving the selected file to the widget window, when theselected file is moved to the widget window, displaying a deviceselection list, and, when at least one device is selected from thedevice selection list, providing the selected file to the selecteddevice, wherein the selected file is provided to the device via a seconddevice that is connected with the first device.

The device selection list may include a list to select the second devicethat is connected with the first device and a list to select a thirddevice that is not connected with the first device.

When the second device is selected from the device selection list, theoperation of providing the selected file may include an operation ofproviding the selected file to the selected second device.

When the third device is selected from the device selection list, themethod may further include inputting a keyword to the widget window anddetecting a device in an address book received from the second devicewherein the device corresponds to the input keyword and providing theselected file may include an operation of providing the selected file tothe detected device.

The keyword may include one of tag values, and the tag values may differfrom each other according to types of applications installed in deviceslisted in the address book.

The first device and the second device may be connected to each othervia Wireless Fidelity (Wi-Fi) communication, and the second device maytransmit data received from the first device to the detected device viaat least one of Third Generation (3G) mobile communication and FourthGeneration (4G) mobile communication.

The first device may include at least one of a Personal Computer (PC), atablet PC, and a smart television (TV), and the second device mayinclude a mobile communication terminal.

The operation of moving the selected file may be performed in a drag anddrop manner.

In accordance with another aspect of the present invention, a firstdevice of transmitting a file by using a widget window is provided. Thefirst device includes a widget window generating unit for displaying adevice selection list when a file stored in the first device is moved tothe widget window on a screen of the first device, and a datatransmitting unit for providing a file to a device selected from thedevice selection list, wherein the file is provided to the selecteddevice via a second device that is connected with the first device.

The device selection list may include the second device that isconnected with the first device and a third device that is not connectedwith the first device.

When the second device is selected from the device selection list, thedata transmitting unit may provide the file to the selected seconddevice.

The first device may further include a detecting unit for detecting adevice corresponding to a keyword that is input to the widget windowwhen the third device is selected from the device selection list, andthe detecting unit may detect the device in an address book receivedfrom the second device, wherein the device corresponds to the keyword.

The data transmitting unit may provide the file to the detected devicevia the second device.

The keyword may include one of tag values, and the tag values may differfrom each other according to types of applications that are installed indevices listed in the address book.

The first device and the second device may be connected to each othervia Wireless Fidelity (Wi-Fi) communication and the second device maytransmit data received from the first device to the detected device viaat least one of Third Generation (3G) mobile communication and FourthGeneration (4G) mobile communication.

The first device may include at least one of a Personal Computer (PC), atablet PC, and a smart TV and the second device may include a mobilecommunication terminal.

The file may be moved to the widget window in a drag and drop manner.

According to another aspect of the present invention, acomputer-readable recording medium having recorded thereon a program forexecuting the method, by using a computer, is provided.

Other aspects, advantages, and salient features of the invention willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainexemplary embodiments of the present invention will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a diagram of a device detection system for data transmissionaccording to an exemplary embodiment of the present invention;

FIG. 2 is a diagram illustrating a structure of a first device accordingto an exemplary embodiment of the present invention;

FIG. 3 is a diagram illustrating a structure of a second deviceaccording to an exemplary embodiment of the present invention;

FIG. 4 is a flowchart of a method of transmitting data between devicesaccording to an exemplary embodiment of the present invention;

FIG. 5 is a flowchart of a method of detecting a device to receive dataaccording to an exemplary embodiment of the present invention;

FIG. 6 is a flowchart of a method of transmitting data between devicesby using a widget window according to an exemplary embodiment of thepresent invention;

FIG. 7 is a flowchart of a method of transmitting data between devicesby using a widget window according to another exemplary embodiment ofthe present invention;

FIG. 8 is a flowchart of a method of receiving and processing callerinformation of a third device performed by the first device, accordingto an exemplary embodiment of the present invention;

FIG. 9 is a flowchart of a method of receiving a captured screen fromthe second device, performed by the first device, according to anexemplary embodiment of the present invention;

FIG. 10 is a diagram illustrating a method of performing communicationbetween devices according to an exemplary embodiment of the presentinvention;

FIG. 11 illustrates an example of an address book according to anexemplary embodiment of the present invention;

FIG. 12 illustrates an example of device detection for data transmissionby the first device according to an exemplary embodiment of the presentinvention;

FIG. 13 illustrates an example of a widget window for displaying aresult of device detection according to an exemplary embodiment of thepresent invention;

FIG. 14 illustrates an example of file transmission based on a filetransmission method that is selected by the first device via a widgetwindow according to an exemplary embodiment of the present invention;

FIG. 15 illustrates an example of file transmission to a transmissiontarget selected by the first device according to an exemplary embodimentof the present invention;

FIG. 16 illustrates an example of message transmission by the firstdevice according to an exemplary embodiment of the present invention;

FIG. 17 illustrates an example in which caller information of the thirddevice is displayed on the first device, and incoming-call connectioninformation regarding whether or not to accept an incoming call from thethird device is generated according to an exemplary embodiment of thepresent invention;

FIG. 18 illustrates an example in which capture information andadditional information are displayed on the first device according to anexemplary embodiment of the present invention; and

FIG. 19 illustrates an example in which the first device receives andoutputs content that is being executed in the second device according toan exemplary embodiment of the present invention.

The same reference numerals are used to represent the same elementsthroughout the drawings.

DETAILED DESCRIPTION OF THE INVENTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of exemplaryembodiments of the invention as defined by the claims and theirequivalents. Accordingly, those of ordinary skill in the art willrecognize that various changes and modifications of the embodimentsdescribed herein can be made without departing from the scope and spiritof the invention. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness. The inventionmay, however, be embodied in many different forms and should not beconstrued as being limited to the exemplary embodiments of the presentinvention set forth herein. Although reference is made to the exemplaryembodiments depicted in the drawings and the following descriptions, theembodiments disclosed herein are not meant to be exhaustive of thevarious alternative designs and embodiments that are encompassed by thedisclosure.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of theinvention. Accordingly, it should be apparent to those skilled in theart that the following description of exemplary embodiments of thepresent invention is provided for illustration purpose only and not forthe purpose of limiting the invention as defined by the appended claimsand their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Throughout the specification, it will also be understood that when anelement is referred to as being “connected to” another element, it canbe directly connected to the other element, or it can be electricallyconnected to the other element by having intervening elements disposedtherebetween. Also, when a part “includes” or “comprises” an element,unless there is a particular description contrary thereto, the part canfurther include other elements, not excluding the other elements.

Expressions such as “at least one of,” when preceding a list ofelements, modify the entire list of elements and do not modify theindividual elements of the list.

FIG. 1 is a diagram of a device detection system for data transmissionaccording to an exemplary embodiment of the present invention.

Referring to FIG. 1, a device detection system includes a first device100, a second device 200, and a third device 300. The first device 100may include at least one of a Personal Computer (PC), a tablet PC, and asmart television (TV), and the second device 200 and the third device300 may include mobile communication terminals, but types of the firstthrough third devices 100, 200, and 300 are not limited thereto.

In the device detection system, the first device 100 may detect thethird device 300 to transmit and receive data using an address bookstored in the second device 200. In this case, the first device 100 mayseparately generate and display a widget window for device detection anddata transmission. When the widget window is selected by a user, thefirst device 100 may provide the user with a service for the devicedetection. The widget window may be an execution window of anapplication that connects the first device 100 and the second device200. Throughout the specification, the term “device detection” refers todetection of at least one of a user list and a device list that areincluded in an address book, i.e., detection of at least one of atelephone number of a device, a user name of a device, an e-mail addressof a device user, and a Social Network Service (SNS) account of a deviceuser, which are included in the address book.

In addition, the first device 100 may exchange data with the thirddevice 300 by using a wireless communication function of the seconddevice 200. When the second device 200 receives a text message from thethird device 300, the first device 100 may also receive the text messagefrom the second device 200 and may display the text message, and thenthe user may check the text message via the first device 100 and mayprovide an answer message to the third device 300 via the second device200.

In another example, when the second device 200 receives a call requestfrom the third device 300, the second device 200 may provide the callerinformation of the third device 300 to the first device 100. In thiscase, the user may check the caller information via the first device 100and may decide whether or not to receive the call request. The user maycheck the caller information of the third device 300 via the firstdevice 100, may write a message related to call reception, and mayprovide the message to the third device 300 via the second device 200.

In yet another example, the first device 100 may provide a file storedin the first device 100 to the second device 200 via a widget window.The first device 100 may also receive content that is being executed inthe second device 200 and output the received content on its associateddisplay.

The first device 100 will be described in more detail with reference toFIG. 2.

FIG. 2 is a diagram illustrating the structure of the first device 100,according to an exemplary embodiment of the present invention.

Referring to FIG. 2, the first device 100 includes a connecting unit110, a data receiving unit 120, a widget window generating unit 130, adata output unit 140, a detecting unit 150, a data transmitting unit160, a DataBase (DB) 170, a transmitting and receiving unit 180, and acontrol unit 190.

The connecting unit 110 connects the first device 100 and the seconddevice 200. In one example, the connecting unit 110 may connect thefirst device 100 and the second device 200 via a user input in a widgetwindow that is generated by the widget window generating unit 130described below. For example, when a user selects a tethering button ofthe widget window, the connecting unit 110 may request the second device200 for the connection. Although a user input is not separately input,if the widget window is executed, the connecting unit 110 may requestthe second device 200 for the connection.

The connecting unit 110 may store the previously received accessinformation from the second device 200, which is for connection to thesecond device 200. The connecting unit 110 may first request connectionto the second device 200 and then may receive the access informationfrom the second device 200. The access information for connectionbetween the first device 100 and the second device 200 may be previouslyset in the first device 100 and the second device 200 by a user.

The data receiving unit 120 receives data from the second device 200.For example, the data receiving unit 120 may receive an address bookthat is stored in the second device 200 and may be used by the firstdevice 100 to detect a device to receive data using a widget window. Inanother example, the data receiving unit 120 may receive informationfrom the second device 200 associated with installed applications in thedevices and may also include the address book. Alternatively,information associated with applications installed in the devices may bestored in the address book.

The data receiving unit 120 may also receive caller information of thethird device 300 from the second device 200. When the third device 300requests a phone call, the data receiving unit 120 may receive thecaller information of the third device 300 from the second device 200,which may be displayed on a screen via the widget window.

In yet another example, the data receiving unit 120 may receive a textmessage via the second device 200. When the second device 200 receivesthe text message from the third device 300, the data receiving unit 120may receive the text message and device information of the third device300 from the second device 200. The device information may include atleast one of a phone number, a user identification value, and anidentification value of an application installed in the device.

Also, the data receiving unit 120 may receive content that is beingexecuted in the second device 200. For example, the data receiving unit120 may receive the content that is being executed in the second device200, in a streaming manner. In another example, when a screen iscaptured in the second device 200, the data receiving unit 120 mayreceive the captured screen of the second device 200.

The widget window generating unit 130 generates a widget window for adata exchange with the second device 200. The widget window may includea detection field for device detection that may be displayed on apre-set area of a background screen of the first device 100. A guidemessage for the device detection may also be displayed in the detectionfield of the widget window. For example, when a keyword is input via thedetection field of the widget window, a device associated with the inputkeyword may be detected.

When a file stored in the first device 100 is moved to the widgetwindow, the widget window generating unit 130 generates a filetransmission method selection window that is used to select of a filetransmission target. The file transmission method selection window mayinclude a list for selecting the target device, such as the seconddevice 200 or the third device 300 that is not connected to the firstdevice 100. For example, the file transmission method selection windowmay include a selection list such as ‘transmission to second device’,‘detection of another device’, or the like. Also, when the third device300 is selected (i.e., when ‘detection of another device’ is selected),a guide message related to a keyword input may be displayed in thedetection field of the widget window.

The data output unit 140 outputs data received from the second device200 on the first device 100. For example, when the detection field ofthe widget window is selected in response to a user input, the dataoutput unit 140 may display the address book received from the seconddevice 200 on a screen of the first device 100.

When the data output unit 140 receives the caller information from thesecond device 200, the data output unit 140 may display the receivedcaller information on the screen of the first device 100. The dataoutput unit 140 may display a message regarding an incoming call on thescreen of the first device 100. In more detail, the data output unit 140may extract a user name and a phone number of the third device 300 fromthe caller information of the third device 300, combine an extractedvalue with a predefined text, and output a guide message regardingwhether or not to accept the incoming call on the first device 100. Forexample, the data output unit 140 may display a guide message saying “Anincoming call from Tom (555-1234). Do you want to accept this call?” onthe screen of the first device 100. When the user rejects to accept theincoming call, the data output unit 140 may display a messagetransmission window for transmission of a predetermined text message onthe screen.

The data output unit 140 may output a text message that is received viathe second device 200 on the screen of the first device 100. When thefirst device 100 receives a message from the third device 300 via thesecond device 200, the data output unit 140 generates a communicationwindow for a message exchange between the first device 100 and the thirddevice 300 and displays the communication window on the screen.

The data output unit 140 may output the content that is being executedin the second device 200 on the first device 100. The data output unit140 may determine an application to execute based on content that isreceived from the second device 200 and may output the content that isbeing executed in the second device 200 using the determinedapplication. For example, when the first device 100 and the seconddevice 200 are connected to each other while a moving picture isreproduced in the second device 200, the data output unit 140 may outputcontent that is streamed from the second device 200 in real-time to thefirst device 100. In this case, application information to execute thereceived content may be previously set and stored in the first device100.

The detecting unit 150 may detect a device to receive data based on auser input via the widget window. When a user selects the widget windowand inputs a keyword to the detection field of the widget window, thedetecting unit 150 may detect a device that corresponds to the inputkeyword from the address book received from the second device 200.

In this example, the keyword input by the user may include a pre-set tagvalue and the detecting unit 150 may filter devices included in theaddress book according to the tag value. The tag value may differ fromanother tag value according to types of data transmission services thatare supported by the devices included in the address book. For example,the tag value may be a prefix value, and in this regard, a prefix ‘A’may be used to detect devices in which Twitter® is installed, and aprefix ‘B’ may be used to detect devices in which Facebook® isinstalled. Thus, when ‘A Tom’ is input to the widget window, thedetecting unit 150 may detect a device whose user name is ‘Tom’ fromamong the devices in which Twitter® is installed. In another example,when ‘B friends’ is input to the widget window, the detecting unit 150may detect a device of a user who is a friend of a user of the firstdevice 100 from among the devices in which Facebook® is installed.

The data transmitting unit 160 transmits data to the third device 300via the second device 200. The data transmitting unit 160 may providethe data to the second device 200 and may transmit the data to the thirddevice 300 by using a communication function of the second device 200.

In more detail, the data transmitting unit 160 may provide a textmessage to the third device 300 via the second device 200. When thethird device 300 is detected and selected in the first device 100 viathe widget window, the communication window for a message exchangebetween the first device 100 and the third device 300 may be generatedin the first device 100. For example, when a text message is input tothe communication window by a user, the first device 100 may transmitthe text message to the third device 300 via the second device 200.

In addition, the data transmitting unit 160 may transmit informationassociated with acceptance of an incoming call. For example, when thethird device 300 requests a phone call to the second device 200, thesecond device 200 may provide the caller information to the first device100. In this case, the first device 100 may provide information relatedto acceptance of an incoming call to the third device 300 via the seconddevice 200. For example, when a user rejects the incoming call, thefirst device 100 may provide the third device 300 with a message relatedto the rejection of the incoming call. For example, an input windowmessage may be displayed on the first device 100 and the user may inputa message saying “I'm in a meeting so I can't receive your call” intothe input window.

The data transmitting unit 160 may also transmit a file stored in thefirst device 100 to the third device 300 via the second device 200. Forexample, the user may select the file stored in the first device 100,may move the selected file to the widget window, may detect the thirddevice 300 via the widget window, and may transmit the selected file tothe third device 300 via the second device 200.

The DB 170 stores information required for the first device 100 todetect the third device 300 by using the address book stored in thesecond device 200 and also stores information required to exchange datawith the second device 200 and the third device 300. For example, the DB170 may store information about the address book that is received fromthe second device 200 and information about types of applicationscorresponding to different tag values.

The transmitting and receiving unit 180 exchanges data with the seconddevice 200 and the third device 300. The transmitting and receiving unit180 may exchange data with the third device 300 via the second device200.

In order to allow the first device 100 to detect the third device 300and exchange data with the second device 200 and the third device 300,the control unit 190 controls the connecting unit 110, the datareceiving unit 120, the widget window generating unit 130, the dataoutput unit 140, the detecting unit 150, the data transmitting unit 160,the DB 170, and the transmitting and receiving unit 180.

Hereinafter, the second device 200 will be described with reference toFIG. 3.

FIG. 3 illustrates an example a structure of the second device 200according to an exemplary embodiment of the present invention.

Referring to FIG. 3, the second device 200 includes a connecting unit210, a data receiving unit 220, a data transmitting unit 230, atransmitting and receiving unit 240, and a control unit 250.

The connecting unit 210 connects the second device 200 and the firstdevice 100 based on a user input via the widget window of the firstdevice 100. For example, when a user selects a tethering button includedin the widget window of the first device 100, the connecting unit 210may receive a connection request from the first device 100.

The connecting unit 210 may provide the first device 100 with accessinformation for connection to the first device 100. The accessinformation may be previously received from the first device 100 and maystore the access information. In another example, the connecting unit210 may first receive a connection request from the first device 100and, in response, provide the access information to the first device100. In yet another example, the access information may be previouslyset in the first device 100 and the second device 200 by a user.

The data receiving unit 220 receives data to be provided to the thirddevice 300 from the first device 100. The data receiving unit 220 mayreceive a text message input to the first device 100. In this example,the data receiving unit 220 may also receive information associated withthe third device 300 from the first device 100. For example, the datareceiving unit 220 may receive an identification value of the thirddevice 300, a phone number of the third device 300, and/or a user nameof the third device 300 from the first device 100.

The data receiving unit 220 may also receive information thatcorresponds to acceptance of an incoming call from the third device 300.For instance, the data receiving unit 220 may receive a call-connectioncommand or a phone call rejection signal from the first device 100. Thedata receiving unit 220 may also receive a message regarding therejection of the incoming call from the first device 100. For example,the data receiving unit 220 may receive a message saying “I'm in ameeting so I can't receive your call.”

Also, the data receiving unit 220 may receive a file from the firstdevice 100. The data receiving unit 220 may receive a file, which isselected and moved to the widget window in the first device 100.

The data transmitting unit 230 also provides the first device 100 withan address book stored in the second device 200. The address book thatis provided to the first device 100 may be used in the first device 100to detect a device to receive data using the widget window. The datatransmitting unit 230 may also provide the first device 100 withinformation about applications installed in devices, the informationincluding the address book. Alternatively, information aboutapplications installed in devices may be included in the address book.

The data transmitting unit 230 provides the first device 100 withcontent that is being executed in the second device 200 in a streamingmanner. In another example, when a predetermined screen is captured inthe second device 200, the data transmitting unit 230 may provide thefirst device 100 with the captured screen of the second device 200.

The data transmitting unit 230 may also provide the third device 300with data that is received from the first device 100. For example, thedata transmitting unit 230 may provide the third device 300 with a textmessage that is received from the first device 100. In another example,the data transmitting unit 230 may provide the first device 100 with atext message that is received from the third device 300.

The data transmitting unit 230 may provide the third device 300 with afile that is received from the first device 100.

The transmitting and receiving unit 240 exchanges information with thefirst device 100 and the third device 300 so that the first device 100may detect a device by using an address book of the second device 200and may provide data to the detected device via the second device 200.

The control unit 250 controls all operations of the second device 200.That is, the control unit 250 controls the connecting unit 210, the datareceiving unit 220, the data transmitting unit 230, and the transmittingand receiving unit 240 so that the second device 200 may provide theaddress book to the first device 100 and data may be exchanged betweenthe first device 100 and the third device 300.

Hereinafter, a method of transmitting data between devices will bedescribed with reference to FIG. 4.

FIG. 4 is a flowchart of a method of transmitting data between devicesaccording to an exemplary embodiment of the present invention.

In operation S400, the first device 100 and the second device 200 areconnected to each other. In operation S400, the first device 100 and thesecond device 200 may be connected to each other based on a user inputvia a widget window of the first device 100. For example, when a userselects a tethering button of the widget window, the first device 100may request connection to the second device 200. In another example, ifthe widget window is executed, the first device 100 may request theconnection to the second device 200. Also, when a screen is captured inthe second device 200, the first device 100 may receive the capturedscreen from the second device 200.

At operation S400, the first device 100 may first request a connectionto the second device 200 and then may receive the access informationfrom the second device 200. Also, the access information for connectionbetween the first device 100 and the second device 200 may be stored orpreviously set in the first device 100 and the second device 200 by auser.

At operation S402, the first device 100 receives data from the seconddevice 200. For example, the first device 100 may receive an addressbook that is stored in the second device 200 and may be used by thefirst device 100 to detect another device to receive data by using thewidget window. The first device 100 may also receive information relatedto applications that are installed in the devices in the address book.Alternatively, information related to applications installed in thedevices may be stored in the address book.

In operation S402, the first device 100 may receive caller informationof the third device 300 from the second device 200. When the thirddevice 300 requests a phone call to the second device 200, the datareceiving unit 120 receives the caller information of the third device300 from the second device 200 and the received caller information maybe displayed on a screen of the first device 100 via the widget window.

Also, in operation S402, the first device 100 may receive a text messagefrom the third device 300 via the second device 200. When the seconddevice 200 receives the text message from the third device 300, thefirst device 100 may receive the text message and device information ofthe third device 300 from the second device 200. The device informationmay include a phone number, a user identification value, and/or anidentification value of an application installed in a device.

Also, in operation S402, the first device 100 may receive content thatis being executed in the second device 200. The first device 100 mayreceive the content that is being executed in the second device 200, forexample, in a streaming manner.

In operation S404, the first device 100 outputs the widget window on itsscreen for a data exchange with the second device 200. The widget windowmay include a detection field for device detection and may be displayedon a predefined area of a background screen of the first device 100. Aguide message may be displayed in the detection field of the widgetwindow for the device detection. Referring to FIG. 4, the widget windowis output after operation S402, but may be output before operation S400or operation S402 to initiate file transfer, for example.

In operation S406, the first device 100 outputs the data that isreceived from the second device 200. When the detection field of thewidget window is selected in response to a user input, the first device100 may display an address book that is received from the second device200 on the screen of the first device 100.

When the first device 100 receives the caller information of the thirddevice 300 from the second device 200, the first device 100 may displaythe received caller information on the screen. In more detail, the firstdevice 100 may extract a user name and a phone number of the thirddevice 300 from the caller information of the third device 300, maycombine the extracted information with a predefined text, and then mayoutput a guide message requesting acceptance of the incoming call. Forexample, the first device 100 may display a guide message stating “Anincoming call from Tom (555-1234). Do you want to receive this call?”When the user rejects the incoming call, the first device 100 maydisplay a message transmission window on the screen to transmit apredetermined text message to the third device 300.

In operation S406, the first device 100 may output a text message thatis received by the second device 200 on its screen. When the firstdevice 100 receives a message of the third device 300 via the seconddevice 200, the first device 100 may generate a communication window fora message exchange between the first device 100 and the third device 300and may display the communication window on its screen.

The first device 100 may output the content that is being executed inthe second device 200. The first device 100 may determine an applicationto execute the content received from the second device 200 and mayoutput the content that is being executed in the second device 200 usingthe determined application. For example, when the first device 100 andthe second device 200 are connected to each other while a moving pictureis reproduced in the second device 200, the first device 100 may outputcontent that is streamed from the second device 200 in real-time to thefirst device 100. In this example, application information to executethe received content may be previously set and stored in the firstdevice 100.

In operation S408, the first device 100 detects a device to receive datausing the widget window based on a user input. When a user selects thewidget window and inputs a predetermined keyword into the detectionfield of the widget window, the first device 100 may detect a devicethat corresponds to the input keyword in the address book. When a filestored in the first device 100 is moved to the widget window, a messagefor guiding a keyword with respect to detection of a device to receivethe file may be displayed in the widget window.

In this case, the keyword that is input by the user may include apredefined tag value and the first device 100 may filter devices in theaddress book according to the tag value. The tag value may correspond todata transmission services that are supported by the devices in theaddress book. For example, the tag value may be a prefix valuecorresponding to a specific service or function. For example, a prefix‘A’ may be used to detect devices having Twitter® is installed and aprefix ‘B’ may be used to detect devices having Facebook® is installed.Thus, when ‘A Tom’ is input to the widget window, the first device 100may detect a device whose user name is ‘Tom’ from among the devices inwhich Twitter® is installed. When ‘B friends’ is input to the widgetwindow, the first device 100 may detect a device of a user who is afriend of a user of the first device 100 from among the devices in whichFacebook® is installed.

In operation S410, the first device 100 provides the second device 200with data that will be provided to the third device 300, such as a textmessage that is input to the first device 100, for example. When thethird device 300 is detected and selected in the first device 100 viathe widget window, the communication window for a message exchangebetween the first device 100 and the third device 300 may be generatedto allow a user to input a text message and may transmit the textmessage to the third device 300 via the second device 200.

At operation S410, the first device 100 may transmit information relatedto acceptance of an incoming call. For example, when the third device300 requests a phone call to the second device 200, the second device200 may provide the caller information to the first device 100. In thiscase, the first device 100 may provide information related to acceptanceof an incoming call to the second device 200. For example, when a userrejects the incoming call from the third device 300, the first device100 may provide the second device 200 with a message related to therejection of the incoming call. For example, an input window for aninput of a call-connection message may be displayed on the first device100 and then the user may input a message stating “I'm in a meeting so Ican't receive your call” into the input window.

In another example of operation S410, the first device 100 may transmita file stored in the first device 100 to the second device 200. When auser selects a file stored in the first device 100, the selected filemay be provided to the second device 200. For example, the user mayselect the file stored in the first device 100 by placing the file inthe widget window, may detect the third device 300 via the widgetwindow, and may provide the second device 200 with an identificationvalue of the third device 300 and the selected file.

In operation S412, the second device 200 provides the third device 300with the data received from the first device 100. For example, thesecond device 200 may provide the third device 300 a text messagereceived from the first device 100, information about a call-connection,and/or a file. In this case, the second device 200 may receive deviceinformation related to the third device 300 (e.g., a phone number, ane-mail address, or the like) from the first device 100 and may transmitthe data to the third device 300 based on the received deviceinformation.

Hereinafter, a method of detecting a device to receive data will bedescribed with reference to FIG. 5.

FIG. 5 is a flowchart of a method of detecting a device to receive data,according to an exemplary embodiment of the present invention.

In operation S500, the first device 100 and the second device 200 may beconnected to each other based on, for example, a user input via a widgetwindow of the first device 100. For example, when a user selects atethering button of the widget window, the first device 100 may requestconnection to the second device 200 to further connect to the thirddevice 300.

In operation S502, the first device 100 receives an address book fromthe second device 200. The address book received from the second device200 may include at least one of a telephone number of a device, a username of a device, an e-mail address of a device user, and an SNS accountof a device user. The address book may be used by the first device 100to detect a device to receive data using the widget window. Also, thefirst device 100 may receive information related to applicationsinstalled in the devices in the address book. Alternatively, informationrelated to applications installed in the devices may be stored in theaddress book.

In operation S504, the first device 100 receives a keyword input fordevice detection via the widget window, which may include a detectionfield for device detection and may be displayed on a predefined area ofa background screen of the first device 100. A guide message for thedevice detection may also be displayed in the detection field of thewidget window. The guide message may be displayed when a file isselected and then is moved to the widget window.

In operation S504, the first device 100 may also receive a keyword thatis input by a user via the widget window. The keyword may include a username of a device or a phone number of a device. In another example, thekeyword may include a tag value associated with a service or a function.For example, the tag value may be a prefix value and detection targetsmay differ from each other according to the tag value. For example, atag value ‘@’ may be used in detection through group names, and a tagvalue ‘#’ may be used in detection through phone numbers. In such anexample, devices in the address book may be filtered according to thetag value. For example, a tag value ‘$’ may be used to filter recentreception and transmission contact addresses of the list, a tag value‘A’ may be used to filter devices in which Twitter® is installed, and atag value ‘B’ may be used to filter devices in which Facebook® isinstalled.

In addition, the widget window may be used to search for contents andmessages that are stored in the first device 100 and the second device200. In this case, a tag value ‘!’ may be used to search for a musicfile, a tag value ‘!!’ may be used to search for a moving picture file,and a tag value ‘&’ may be used to search for a message.

The widget window may be used to detect a peripheral device connected tothe first device 100. For example, a tag value ‘{circumflex over ( )}’may be used to detect the peripheral device by using Digital LivingNetwork Alliance (DLNA).

In operation S506, the first device 100 may detect the devices relatedto the input keyword in the address book. In this case, the first device100 may filter devices in which Twitter® is installed, and a prefix ‘B’may be used to detect devices in which Facebook® is installed. Thus,when ‘A Tom’ is input to the widget window, the first device 100 mayfilter the devices in which Twitter® is installed and then may detect adevice whose user name is ‘Tom’ from among the filtered devices. Also,when ‘B friends’ is input to the widget window, the first device 100 mayfilter the devices in which Facebook® is installed and then may detect adevice of a user who is a friend of the user of the first device 100from among the filtered devices.

In operation S508, the first device 100 may provide the second device200 with the data to be provided to the detected third device 300. Forexample, the first device 100 may provide the second device 200 with atext message input by the user or a file selected by the user. The firstdevice 100 may also provide the second device 200 with deviceinformation of the third device 300 to receive the data including a username, a phone number, and/or an e-mail address of a user, for example.

In operation S510, the second device 200 transmits the data receivedfrom the first device 100 to the third device 300 using the deviceinformation of the third device 300.

Hereinafter, a method of transmitting data between devices by using awidget window will be described with reference to FIG. 6.

FIG. 6 is a flowchart of a method of transmitting data between devicesby using a widget window, according to an exemplary embodiment of thepresent invention.

In operation S600, the first device 100 and the second device 200 may beconnected to each other based on a user input via a widget window. Forexample, when a user selects a tethering button of the widget window,the first device 100 may request connection to the second device 200. Inother examples, the second device 200 may request connection to thefirst device 100.

In operation S602, in response to the user input, the first device 100may move a file that is selected to the widget window. For example, theuser may select a file stored in the first device 100 and move theselected file to the widget window in a drag and drop manner.

In operation S604, the first device 100 may display a file transmissionmethod selection window on the screen to allow a user to select a filetransmission method. The file transmission method selection windowincludes a list containing ‘file transmission’ for direct filetransmission and ‘message transmission’ for file transmission via amessage window.

In operation S606, the first device 100 determines whether ‘filetransmission’ is selected in the file transmission method selectionwindow. If ‘file transmission’ is selected according to a user input atoperation S606, the first device 100 directly transmits a file to thesecond device 200 in operation S608.

Also, in operation S606, if ‘file transmission’ is not selected, inoperation S610, the first device 100 determines whether ‘messagetransmission’ is selected in the file transmission method selectionwindow.

In operation S610, if ‘message transmission’ is selected, in operationS612, the first device 100 detects a transmission target. In operationS612, the first device 100 may receive a keyword to detect thetransmission target by using a keyword input by the user.

In this case, the keyword may include a user name of a device, a phonenumber of the device, or a tag value. For example, the tag value may bea prefix value corresponding to data transmission services that aresupported by devices included in the address book. The first device 100may filter the device by using the tag value included in the keyword.For example, a prefix ‘A’ may be used to detect devices in whichTwitter® is installed, and a prefix ‘B’ may be used to detect devices inwhich Facebook® is installed. Thus, when ‘A Tom’ is input to the widgetwindow, the first device 100 may filter the devices in which Twitter® isinstalled and then may detect a device whose user name is ‘Tom’ from thefiltered devices. When ‘B friends’ is input to the widget window, thefirst device 100 may filter the devices in which Facebook® is installedand then may detect a device of a user who is a friend of the user ofthe first device 100 from the filtered devices. The first device 100selects at least one of the detected devices as a transmission target inthe address book that is received from the second device 200.

In operation S614, the first device 100 may generate the messagetransmission window with respect to the device detected in operationS612 and may insert the file into the generated message transmissionwindow.

However, whether or not to display the file transmission methodselection window on the first device 100 may be decided according to astate of the second device 200. For example, when the messagetransmission window is displayed on the second device 200, the firstdevice 100 may not display the file transmission method selectionwindow.

Display of the file transmission method selection window on the firstdevice 100 may be decided according to a state of the first device 100.For example, when a message transmission window is displayed on thefirst device 100, the first device 100 may not display the filetransmission method selection window. Also, the first device 100 mayinsert the selected file into the message transmission window displayedon the first device 100.

In operations S616 and S618, the first device 100 provides the selectedfile to the third device 300 via the second device 200. In such anexample, the third device 300 may be the device that is selected inoperation S612.

Hereinafter, a method of transmitting data between devices by using awidget window will be described with reference to FIG. 7.

FIG. 7 is a flowchart of a method of transmitting data between devicesby using a widget window, according to another exemplary embodiment ofthe present invention.

In operation S700, the first device 100 and the second device 200 may beconnected to each other based on a user input via a widget window of thefirst device 100. For example, when a user selects a tethering button ofthe widget window, the first device 100 may request connection to thesecond device 200. In other examples, the second device 200 may requestconnection to the first device 100.

In operation S702, the first device 100 may move a file to the widgetwindow that is selected in response to the user input. The user mayselect a file stored in the first device 100 and may move the selectedfile to the widget window in a drag and drop manner.

In operation S704, the first device 100 outputs a selection list toselect a target to receive the selected file. In operation S704, thefirst device 100 may display a file transmission target selection windowon the screen that includes a list containing ‘transmission to connecteddevice’ for file transmission to the second device 200 and ‘transmissionto another device’ for file transmission to a device that is notconnected to the first device 100.

In operation S706, the first device 100 determines whether ‘transmissionto connected device’ is selected in the file transmission targetselection window. In operation S706, when ‘transmission to connecteddevice’ is selected according to a user input, the first device 100directly transmits the selected file to the second device 200 inoperation S708.

Returning to operation S706, when ‘transmission to connected device’ isnot selected, the first device 100 determines whether ‘transmission toanother device’ is selected in the file transmission target selectionwindow in operation S710.

In operation S710, when ‘transmission to another device’ is selected,the first device 100 detects a device to receive a file at operationS712. In operation S712, the first device 100 may receive a keyword tobe used in detecting and selecting the device to receive a file.

In operations S714 and S716, the first device 100 provides the selectedfile to the third device 300 via the second device 200. In this example,the third device 300 may be the device that is detected in operationS712.

Hereinafter, a method of receiving and processing caller information ofthe third device 300, performed by the first device 100, will bedescribed with reference to FIG. 8.

FIG. 8 is a flowchart of a method of receiving and processing callerinformation of the third device 300, according to an exemplaryembodiment of the present invention.

In operation S800, the first device 100 and the second device 200 may beconnected to each other based on a user input via a widget window of thefirst device 100. For example, when a user selects a tethering button ofthe widget window, the first device 100 may request connection to thesecond device 200. In other examples, the second device 200 may requestconnection to the first device 100.

In operation S802, the third device 300 requests call-connection to thefirst device 100 via the second device 200. The second device 200 mayreceive a call signal from the third device 300 including the callerinformation at operation S802.

In operation S804, the second device 200 may provide the first device100 with the caller information of the third device 300. For example,the second device 200 may receive a phone number from the third device300, may extract a user name, a group name, and the like with respect tothe received phone number from an address book and transmit the callerinformation, including information from the address book to, the firstdevice 100 with the caller information of the third device 300.

In operation S806, the first device 100 may display the received callerinformation on a separate window on a screen of the first device 100.

In operation S808, the first device 100 may display a selection menu inthe display associated with the caller information. The selection menumay include items incoming-call connection information such as ‘acceptincoming call’, ‘reject incoming call’, and ‘reject with message.’

In operation S810, the first device 100 generates incoming-callconnection information according to the incoming-call connectioninformation. The incoming-call connection information may include acommand to accept the incoming call, a command to reject the incomingcall, and a message regarding incoming-call connection. The first device100 generates a command to accept the incoming call from the thirddevice 300 based on the selected incoming-call connection information.For example, when a user selects ‘accept incoming call’ in the selectionmenu, the first device 100 generates a command to accept acall-connection with the third device 300. When the user selects ‘rejectincoming call’ in the selection menu, the first device 100 may generatea command to reject the call-connection with the third device 300.

When the user selects ‘reject with message’ in the selection menu, thefirst device 100 may display a message input window on the screen andgenerate a message regarding whether or not to accept the incoming call.For example, the first device 100 may generate a message saying “I'm ina meeting so I can't receive your call,” based on the user input to themessage input window. The message input window may be separatelydisplayed in the pop-up window that displays the caller information.

In operation S812, the first device 100 may provide the second device200 with the command to accept the incoming call, the command to rejectthe incoming call, and/or the message regarding incoming-callconnection. When the first device 100 provides the second device 200with the command to accept the incoming call, the second device 200 maybe connected to the third device 300 and may perform thecall-connection.

In operation S814, the second device 200 provides the message regardingincoming-call connection to the third device 300. When the first device100 provides the command to reject the incoming call to the seconddevice 200, the second device 200 may block the call-connection with thethird device 300. Also, the second device 200 may provide the thirddevice 300 with a message received from the first device 100.

Hereinafter, a method of receiving a captured screen from the seconddevice 200 will be described with reference to FIG. 9.

FIG. 9 is a flowchart of a method of receiving a captured screen fromthe second device 200, according to an exemplary embodiment of thepresent invention.

In operation S900, in response to a user input, the first device 100selects a capture icon in a widget window. The capture icon may includean icon to capture a screen of the second device 200 and an icon to takea picture by using the second device 200. One capture icon may be in thewidget window and, when the capture icon is selected, a selection windowfor selection of capture types may be displayed. In this case, a usermay select one of the capture types in the selection window and decidewhether to capture the screen of the second device 200 or to take apicture by using the second device 200.

In operation S902, the first device 100 may request capture information.For example, the capture information may include a captured screen imageof the second device 200 or an image captured by the second device 200.

In operation S904, in response to the request for the captureinformation, the second device 200 generates the captured screen image.When the first device 100 requests the capture information, the seconddevice 200 may generate the captured screen image of the second device200 in operation S904.

In operation S906, the second device 200 generates the captured image,in response to the request for the capture information. In operationS902, when the first device 100 requests the capture informationincluding the image captured by the second device 200, in operationS906, the second device 200 may generate the captured image by using aphotographing apparatus included in the second device 200.

In operation S908, the second device 200 generates context informationrelated to at least one of a screen capturing operation and an imagephotographing operation. The context information may include a time, aplace, and weather, for example.

In operation S910, the second device 200 provides the captureinformation to the first device 100. The capture information may includethe captured screen image, the captured image, and the contextinformation.

In operation S912, the first device 100 collects additional informationfrom a server (not shown) based on the context information. In operationS912, the first device 100 may check the context information included inthe capture information and then may collect the additional informationcorresponding to the context information. For example, the additionalinformation may include map information, area information, and newsinformation, for example.

In operation S914, the first device 100 displays the received captureinformation and the additional information on the screen. The firstdevice 100 may display at least one of the captured screen image and thecaptured image, and may also display the context information and theadditional information which are related to the captured screen imageand/or the captured image.

Hereinafter, a method of performing communication between devices willbe described with reference to FIG. 10.

FIG. 10 is a diagram illustrating a method of performing communicationbetween devices, according to an exemplary embodiment of the presentinvention.

Referring to FIG. 10, the first device 100 may use a wirelesscommunication function of the second device 200 via tethering. Forexample, the first device 100 may be connected with the second device200 via Wireless Fidelity (Wi-Fi) communication. Also, the first device100 and the second device 200 may be connected to each other by using adifferent wireless communication service such as a Third Generation (3G)mobile communication or the Fourth Generation (4G) mobile communication.

In this case, a tethering function of the second device 200 may beactivated in response to a user input in a widget window in the firstdevice 100. For example, when a predetermined region is selected in thewidget window displayed in the first device 100, the first device 100may request the second device 200 for activation of the tetheringfunction. That is, when the widget window is active in the first device100, the first device 100 may request the second device 200 for thetethering function.

Also, the first device 100 and the second device 200 may exchange accessinformation for communication when the tethering function is requested.

For example, a widget window application to perform device detection anddata transmission using a widget window may be executed in the firstdevice 100. In this example, the first device 100 and the second device200 may be connected to each other by using the widget windowapplication. Also, a widget window agent in the widget windowapplication that may be executed when a power of the first device 100 isON and may execute the widget window in the first device 100 when aperipheral device for connection exists at a same Access Point (AP) asthat of the first device 100. The widget window application may detectthe second device 200 and connect the first device 100 and the detectedsecond device 200. In more detail, the widget window application maydetect the second device 200 that is a peripheral device of the firstdevice 100 and transmit an authentication code to the detected seconddevice 200. The second device 200 may confirm the authentication codeand perform Wi-Fi communication configuration for connection to thefirst device 100. Also, the second device 200 may provide the firstdevice 100 with an Internet Protocol (IP) value and a verifiedauthentication code. The widget window application may authenticate thedetected second device 200 to connect the first device 100 and thesecond device 200. After the authentication is performed between thefirst device 100 and the second device 200, the first device 100 and thesecond device 200 may be connected to each other without separateauthentication.

In another example, the first device 100 and the second device 200 maybe connected to each other by using a Universal Serial Bus (USB) cable.In this example, the widget window application of the first device 100may execute the widget window on a screen of the first device 100 andrequest the second device 200 to execute a widget window application ofthe second device 200. Also, when the USB connection between the firstdevice 100 and the second device 200 is disconnected, the first device100 and the second device 200 may be re-connected to each other viaWi-Fi communication.

Hereinafter, an address book will be described with reference to FIG.11.

FIG. 11 illustrates an example of an address book according to anexemplary embodiment of the present invention.

Referring to FIG. 11, the address book includes a speed-dial field 90, auser field 91, a phone number field 92, a group field 93, a device field94, and an application field 95.

Speed-dials corresponding to phone numbers are recorded in thespeed-dial field 90 and user names corresponding to the phone numbersare recorded in the user field 91. The phone numbers are recorded in thephone number field 92 and group names of the user are recorded in thegroup field 93. In the address book, types of devices corresponding tothe phone numbers are recorded in the device field 94. For example,device names such as ‘Galaxy S3’ and ‘I-Phone’ may be recorded in thedevice field 94. Names of applications that are installed in the devicesare recorded in the application field 95. For example, names ofmessenger applications such as Twitter® and Facebook® may be recorded inthe application field 95. The address book may be directly provided fromthe second device 200 to the first device 100 or may be indirectlyprovided from the second device 200 to the first device 100 via aseparate server (not shown), and the first device 100 may detect adevice to receive data using the address book.

Also, prefixes may match with names of the devices recorded in thedevice field 94 and the names of applications recorded in theapplication field 95, respectively. Thus, when a user inputs a keywordfor device detection, the user may also input a predetermined prefix tofilter some of the devices by using the input prefix and performdetection with respect to the filtered devices.

Hereinafter, an example of device detection for data transmission by thefirst device 100 will be described with reference to FIG. 12.

FIG. 12 illustrates an example of device detection for data transmissionby the first device 100, according to an exemplary embodiment of thepresent invention.

Referring to FIG. 12, a widget window 12 for data transmission may bedisplayed on a screen 10 of the first device 100. When a predeterminedbutton 14 is selected in the widget window 12, the first device 100 andthe second device 200 may be connected to each other. In anotherexample, when the widget window 12 is active in the first device 100,the first device 100 and the second device 200 may be connected to eachother.

Also, a user may input a keyword into a detection field 16 of the widgetwindow 12 to detect a target to receive data. For example, when the userinputs ‘B friends’ into the detection field 16, the first device 100 mayfilter devices from an address book by using a prefix ‘B’ and detect adevice that belongs to a friend of the user from among the filtereddevices

The detection result may be output to a separate window 17 andapplications that are installed in the user's device may be displayed ona region 18 of the output result. When the region 18 is selected, acorresponding application may be executed in the second device 200 totransmit data to the detected device via the second device 200. In thisexample, the first device 100 may provide the second device 200 with acontrol command to execute the application and the data to betransmitted.

Hereinafter, an example of a widget window for displaying a result ofdevice detection will be described with reference to FIG. 13.

FIG. 13 illustrates an example of a widget window for displaying aresult of device detection, according to an exemplary embodiment of thepresent invention.

Referring to FIG. 13, when a keyword ‘Kim’ is input to a detection field16 of a widget window 12, a device detection list 1 corresponding to thekeyword ‘Kim’ is displayed below the widget window 12. As illustrated inFIG. 13, the device detection list 1 may include user names and phonenumbers of detected devices. The device detection list 1 may alsoinclude a recent device detection list 2 of devices that are recentlyused by a user that is distinguishably displayed on an upper portion ofthe device detection list 1.

The device detection list 1 may include a calling icon 3 and a messagetransmission icon 4. When the user selects the calling icon 3, the firstdevice 100 may request the second device 200 to make a call to a devicedisplayed on the detection list 1. When the user selects the messagetransmission icon 4, a message transmission window (not shown) isdisplayed on a screen of the first device 100 and the first device 100may transmit a message, which is input to the message transmissionwindow, to the third device 300 via the second device 200.

In addition, a plurality of icons 5 is displayed on the widget window 12to allow functions to be performed in the first device 100. For example,the icons 5 may include an icon for movement to a home-screen, an iconfor reproduction of music, an icon for execution of an internet browser,and an icon for a request for a captured image. When the user selectsthe icon for a request for a captured image, the first device 100 mayrequest the second device 200 for a captured screen image of the seconddevice 200. Also, when the user selects the icon for a request for acaptured image, the first device 100 may request the second device 200for an image captured by the second device 200.

Hereinafter, an example of file transmission based on a filetransmission method that is selected by the first device 100 via awidget window will be described with reference to FIG. 14.

FIG. 14 illustrates an example of file transmission based on a filetransmission method that is selected by the first device 100 via awidget window, according to an exemplary embodiment of the presentinvention.

Referring to FIG. 14, when a user selects a file 21 from a folder 20that is displayed on a screen 10 of the first device 100 and moves theselected file 21 to a widget window 12, a selection window 23 may bedisplayed on the screen 10 for selection of a file transmission method.The selection window 23 may include a list containing ‘filetransmission’ for direct file transmission and ‘message transmission’for file transmission via a message.

When ‘file transmission’ is selected from the selection list, the firstdevice 100 may provide a selected file to the second device 200 withouta separate procedure. When ‘message transmission’ is selected from theselection list, a guide message related to a keyword input may bedisplayed in a detection field 16 of the widget window 12. In response,the user may input a keyword to the detection field 16 to detect adevice, and the second device 200 may generate a message transmissionwindow 24 with respect to the detected device and insert the selectedfile into the message transmission window 24. The first device 100 mayprovide the file inserted into the message transmission window 24 to thedetected device via the second device 200.

Hereinafter, an example of file transmission to a file transmissiontarget selected by the first device 100 will be described with referenceto FIG. 15.

FIG. 15 illustrates an example of file transmission to a filetransmission target selected by the first device 100, according to anexemplary embodiment of the present invention.

Referring to FIG. 15, when a user selects a file 21 from a folder 20displayed on a screen 10 of the first device 100 and moves the file 21to a widget window 12, a selection window 22 is displayed for selectionof a transmission target.

For example, the selection window 22 may include a selection list suchas ‘transmission to second device’ and ‘detection of another device’.When the second device 200 is selected from the selection list, thefirst device 100 may provide the selected file 21 to the second device200 without a separate procedure. When the third device 300 is selectedfrom the selection list (i.e., when ‘detection of another device’ isselected), a guide message related to a keyword input may be displayedin a detection field 16 of the widget window 12. Then, the user mayinput a keyword to the detection field 16 to detect a device and providethe selected file 21 to the detected device via the second device 200.

FIG. 16 illustrates an example of message transmission by the firstdevice 100, according to an exemplary embodiment of the presentinvention.

Referring to FIG. 16, when the second device 200 receives a message fromthe third device 300, the second device 200 may provide the receivedmessage to the first device 100, which displays the received message ona message window 30. A user may input a message to the message window 30and the input message may be provided to the third device 300 via thesecond device 200. Also, the user may detect another device by using awidget window 12 to provide a message to the other detected device viathe message window 30.

FIG. 17 illustrates an example in which caller information of the thirddevice 300 is displayed on the first device 100 and incoming-callconnection information related to acceptance of an incoming call fromthe third device 300 is generated according to an exemplary embodimentof the present invention.

Referring to FIG. 17, when the third device 300 attempts to make a phonecall to the second device 200, the second device 200 may provide thecaller information of the third device 300 to the first device 100. Inthis example, the first device 100 may receive the caller informationand may display the caller information on a call reception notice window40. Afterward, a user may select an ‘accept’ button 41, a ‘reject’button 42, or a ‘reject with message’ button 43 to accept or reject anincoming call. In response, the first device 100 may generate theincoming-call connection information based on the selection. Forexample, when the user selects the ‘accept’ button 41, the first device100 may generate a command to accept the incoming call and provide thecommand to the second device 200.

When the user selects the ‘reject’ button 42, the first device 100 maygenerate a command to reject the incoming call and then may provide thecommand to the second device 200.

In another example, when the user selects the ‘reject with message’button 43, the first device 100 may generate a command to reject theincoming call, provide the command to the second device 200, andgenerate and display a separate message input window 44 related toacceptance or rejection of the call. For example, the user may input amessage saying “I'm in a meeting so I can't receive your call” to themessage input window 44 and then the first device 100 may provide theinput message to the third device 300 via the second device 200.

FIG. 18 illustrates an example in which capture information andadditional information are displayed on the first device 100 accordingto an exemplary embodiment of the present invention.

When the first device 100 requests a captured image from the seconddevice 200, the second device 200 may provide the first device 100 withcapture information including the captured image. The first device 100may collect additional information from a server (not shown) by usingcontext information included in the capture information.

The capture information and the additional information are illustratedin the example of FIG. 18. An image 60 captured by the second device200, location information 62 about where the image 60 was captured, andmap information 63 illustrating the location may be displayed on ascreen of the first device 100.

FIG. 19 illustrates an example in which the first device 100 receivesand outputs content that is being executed in the second device 200,according to an exemplary embodiment of the present invention.

Referring to FIG. 19, when the user selects a predetermined button in awidget window 12 displayed on the first device 100, content that isbeing executed in the second device 200 may be provided to the firstdevice 100. The second device 200 may stream the content to the firstdevice 100 in real-time, which may execute an application 50 toreproduce the streamed content according to a type of the streamedcontent.

According to the one or more exemplary embodiments of the presentinvention, a transmission target may be effectively selected by using awidget window and data may be transmitted to the file transmissiontarget.

Also, according to the one or more exemplary embodiments of the presentinvention, a transmission target may be detected from an address bookstored in another device and, using the widget window, data may betransmitted to the detected transmission target via the other device.

While the invention has been shown and described with reference tocertain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the invention asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method of transmitting, by a computer, a fileby using an execution window of an application that connects thecomputer to a first mobile terminal, the method comprising: receiving anaddress book stored in the first mobile terminal from the first mobileterminal; moving a file selected on a screen of the computer to theexecution window of the application; when the file is moved to theexecution window, receiving a keyword that is input to the executionwindow; detecting at least one second mobile terminal corresponding tothe keyword from the received address book; and transmitting the filefrom the computer to the at least one second mobile terminal via thefirst mobile terminal, wherein the keyword comprises a textual prefixtag value, and detection targets of the keyword differ from each otheraccording to the textual prefix tag value, the textual prefix tag valuecorresponding to at least one of a plurality of types of datatransmission services supported by the at least one second mobileterminal.
 2. The method of claim 1, wherein the transmitting of the filecomprises transmitting the file to the first mobile terminal that isconnected with the computer.
 3. The method of claim 1, wherein acommunication method between the computer and the first mobile terminalis different from a communication method between the at least one secondmobile terminal and the first mobile terminal.
 4. The method of claim 3,wherein the computer and the first mobile terminal are connected to eachother via Wireless Fidelity (Wi-Fi™) communication, and the at least onesecond mobile terminal and the first mobile terminal are connected viacellular mobile communication.
 5. The method of claim 1, wherein thetransmitting of the file from the computer to the at least one secondmobile terminal via the first mobile terminal comprises: generating amessage input window; inserting the file into the message input window;and providing the file to the first mobile terminal.
 6. The method ofclaim 1, wherein the moving comprises moving the file to the executionwindow in a drag and drop manner.
 7. A method of transmitting, by afirst mobile terminal connected with a computer, a file received fromthe computer to at least one second mobile terminal, the methodcomprising: transmitting an address book stored in the first mobileterminal to the computer; receiving, by the first mobile terminal, thefile from the computer, in response to the file being selected on ascreen of the computer and moved to an execution window of anapplication that connects the computer and the first mobile terminal;receiving a keyword that is input to the execution window from thecomputer; detecting the at least one second mobile terminalcorresponding to the keyword from the address book; transmitting fromthe computer, by the first mobile terminal, the file to the at least onesecond mobile terminal that is connectable with the first mobileterminal; and transmitting information stored in the first mobileterminal to the computer to detect the at least one second mobileterminal, wherein the keyword comprises a textual prefix tag value, anddetection targets of the keyword differ from each other according to thetextual prefix tag value, the textual prefix tag value corresponding toat least one of a plurality of types of data transmission servicessupported by the at least one second mobile terminal.
 8. The method ofclaim 7, wherein a communication method between the computer and thefirst mobile terminal is different from a communication method betweenthe first mobile terminal and the at least one second mobile terminal.9. The method of claim 8, wherein the computer and the first mobileterminal are connected to each other via Wireless Fidelity (Wi-Fi™)communication, and the first mobile terminal and the at least one secondmobile terminal are connected to each other via cellular mobilecommunication.
 10. The method of claim 7, wherein the receiving of thefile comprises receiving the file from the computer via a message, andwherein the file is inserted into a message input window that isgenerated by the computer when the at least one second mobile terminalis selected from the address book.
 11. A computer for transmitting afile by using an execution window of an application, the computercomprising: one or more processors; at least one memory; and one or moreprograms, wherein the one or more programs are stored in the at leastone memory and configured to be executed by the one or more processors,the one or more programs including instructions to: receive a keywordthat is input to the execution window, receive an address book stored ina first mobile terminal to detect a second mobile terminal connectablewith the first mobile terminal from the first mobile terminal, detect atleast one second mobile terminal corresponding to the keyword from thereceived address book, and transmit the file from the computer to the atleast one second mobile terminal via the first mobile terminal, andwherein the keyword comprises a textual prefix tag value, and detectiontargets of the keyword differ from each other according to the textualprefix tag value, the textual prefix tag value corresponding to at leastone of a plurality of types of data transmission services supported bythe at least one second mobile terminal.
 12. The computer of claim 11,wherein the file is transmitted to the first mobile terminal.
 13. Thecomputer of claim 11, wherein a communication method between thecomputer and the first mobile terminal is different from a communicationmethod between the at least one second mobile terminal and the firstmobile terminal.
 14. The computer of claim 13, wherein the computer andthe first mobile terminal are connected to each other via WirelessFidelity (Wi-Fi™) communication, and the at least one second mobileterminal and the first mobile terminal are connected to each other viacellular mobile communication.
 15. The computer of claim 11, wherein thetransmitting the file from the computer to the at least one secondmobile terminal via the first mobile terminal comprises: generating amessage input window, inserting the file into the message input window,and providing the file to the first mobile terminal.
 16. The computer ofclaim 11, wherein the file is moved to the execution window in a dragand drop manner.
 17. A first mobile terminal comprising: a touchsensitive display; one or more processors; at least one memory; and oneor more programs, wherein the one or more programs are stored in the atleast one memory and configured to be executed by the one or moreprocessors, the one or more programs including instructions to: receivea file from a computer when the file is selected and moved to anexecution window of an application that connects the computer and thefirst mobile terminal, transmit an address book stored in the firstmobile terminal to the computer, receive a keyword that is input to theexecution window from the computer, detect at least one second mobileterminal corresponding to the keyword from the address book, transmitthe file to the at least one second mobile terminal that is connectablewith the first mobile terminal, and transmit information stored in thefirst mobile terminal to the computer to detect the at least one secondmobile terminal, and wherein the keyword comprises a textual prefix tagvalue, and detection targets of the keyword differ from each otheraccording to the textual prefix tag value, the textual prefix tag valuecorresponding to at least one of a plurality of types of datatransmission services supported by the at least one second mobileterminal.
 18. The first mobile terminal of claim 17, wherein acommunication method between the computer and the first mobile terminalis different from a communication method between the first mobileterminal and the at least one second mobile terminal.
 19. The firstmobile terminal of claim 18, wherein the computer and the first mobileterminal are connected to each other via Wireless Fidelity (Wi-Fi™)communication, and the first mobile terminal and the at least one secondmobile terminal are connected to each other via cellular mobilecommunication.
 20. The first mobile terminal of claim 17, wherein thefile is further received from the computer via a message, and whereinthe file is inserted into a message input window that is generated bythe computer when the at least one second mobile terminal is selectedfrom the address book.
 21. The first mobile terminal of claim 17,wherein the address book is transmitted from the first mobile terminalto the computer, and wherein the address book is used to detect a targetto receive the file in response to the keyword that is input to theexecution window.
 22. The first mobile terminal of claim 17, wherein acommunication comprises at least one of a text message or callinformation associated with a call from a user of the at least onesecond mobile terminal.
 23. A non-transitory computer-readable recordingmedium having a program recorded thereon, the program causing a computerto execute the method of claim
 1. 24. A non-transitory computer-readablerecording medium having a program recorded thereon, the program causinga computer to execute the method of claim 7.